Skip to content

Conversation

cnadler86
Copy link
Contributor

@cnadler86 cnadler86 commented Sep 30, 2025

Description

This fixes the issue of having a LOG Error entry on no peripheral is connected to the GDMA channel. This happens because a missing call to the respective connect function and while deinit calling the disconnect function. See #750

Fix #750

Testing

Camera still works as expected (Tested on a esp32S3 with IDF 5.4.2)

Checklist

Before submitting a Pull Request, please ensure the following:

  • 🚨 This PR does not introduce breaking changes.
  • All CI checks (GH Actions) pass.
  • Documentation is updated as needed.
  • Tests are updated or added as necessary.
  • Code is well-commented, especially in complex areas.
  • Git history is clean — commits are squashed to the minimum necessary.

@cnadler86
Copy link
Contributor Author

In order to better illustrate that deleting the line will not affect the functionality, here the code snippet of the gdma_disconnect function:

esp_err_t gdma_disconnect(gdma_channel_handle_t dma_chan)
{
    ESP_RETURN_ON_FALSE(dma_chan, ESP_ERR_INVALID_ARG, TAG, "invalid argument");
    ESP_RETURN_ON_FALSE(dma_chan->periph_id != GDMA_INVALID_PERIPH_TRIG, ESP_ERR_INVALID_STATE, TAG, "no peripheral is connected to the channel");
...
}

This PR just deletes the call to this function, which returns after the second statement doing nothing but throwing an unnecessary error log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ESP32-S3 esp32-camera: gdma_disconnect error during esp_camera_deinit() due to ll_cam.c not calling gdma_connect()

1 participant